Is it considered a best practice to have the IIS server on Exchange 2010, that serves up the OWA pages, automatically redirect regular http requests to the server, so that they get properly redirected to httpS:// ? If so, which IIS directories would I need to make this change under?

The way that I do this is to just have HTML code in the root of the web site to do the redirection - so end users go to http://host.example.com and get redirected to https://host.example.com/owa However my preference is to not open port 80 to the Exchange server from the internet at all as I consider that a security risk. Make the users enter https:// - they will complain but tough. However if you want to catch everything then follow this: http://briandesmond.com/blog/redirecting-owa-urls-in-exchange-2010/ Simon.Simon Butler, Exchange MVP Blog | Exchange Resources | In the UK? Hire Me.

Hi, You can refer to the article below: Simplify the Outlook Web App URL http://technet.microsoft.com/en-us/library/aa998359.aspxXiu Zhang TechNet Community Support

You could have your NLBs handle the redirection for you (if you are using NLBs). The way we handled this is to create a separate site on the same server that only responds to http://<CAS or CAS Array>, and uses IIS redirection to redirect all port 80 requests to the default site which does not allow unsecure connections. You could do this with redirection on the default site, but remember, using IIS redirection affects ALL directories under the root unless you go to each individual directory and modify it. The was a PITA, so a secondary site was easier and cleaner.

Hi, You can refer to the article below: Simplify the Outlook Web App URL http://technet.microsoft.com/en-us/library/aa998359.aspxXiu Zhang TechNet Community Support